This is a request for a a11y review of the translations feature.

The areas that are ready for review are:

• Main Flow
• Page Settings
• First part of Global settings

Right now, the feature is locked behind a Nimbus flag. Please use Nimbus CLI to unlock the feature or request an Android APK with the feature unlocked from :olivia.

To Use Nimbus CLI:

• Download Nimbus CLI here
• Send the following command (for a Nightly build):
  • nimbus-cli --app fenix --channel nightly test-feature translations --no-validate ~/Desktop/translations-all-enabled.json
  • Where the file translations-all-enabled.json contains:

{
  "main-flow-toolbar-enabled" : true,
  "main-flow-browser-menu-enabled" : true,
  "page-settings-enabled" : true,
  "global-settings-enabled" : true,
  "global-lang-settings-enabled" : false,
  "global-site-settings-enabled" : false,
  "downloads-enabled" : false
}

The feature is successfully enabled if "Translate page" is available on the toolbar while visiting a website.

For more details on how the feature works, this document provides an overview originally written for QA.

A quick summary of using the feature:

• Navigate to a page not in the device or app language that is in a translatable language
  • I usually test on www.wikipedia.org and navigate to other languages or www.mozilla.org/fr for the Mozilla French website
• A toolbar icon will appear titled "Translate page", press that to translate OR access via the browser menu and then "Translate page"

Please provide an explanation of the feature or change. Include a description of the user scenario in which it would be used and how the user would complete the task(s).

This feature allows users to translate webpages on Android. The primary scenario is when a user visits a website on a language the user does not know. The feature offers the user the option to translate on the toolbar. The user would open the feature and press translate to complete the main flow to translate the page into a known user language.

Screenshots and visual UI specs are welcome, but please include sufficient accompanying explanation so that blind members of the accessibility team are able to understand the feature/change.

• Figma
• Written Description of Feature Areas

How do we test this?

If there is an implementation to test, please provide instructions for testing it; e.g. setting preferences, other preparation, how to trigger the UI, etc.

Recommended scenarios:

Scenario 1 - Basic Toolbar Translate:

• A user on an English language device and app navigates to a French website.
• A toolbar option titled "Translate page" will appear on the toolbar.
  • Note, under some conditions, the translations dialog will automatically popup.
• A translations dialog will appear on the screen.
• Set "To" and "From" languages and press translate to begin translating.
• The page should begin to translate.

Scenario 1a - Basic Translate Restore:

• Follow the steps in scenario 1.
• Navigate to the toolbar, the translation option should now be identified as "Page translated from French to English".
• Open "Page translated from French to English".
• Press "Show original".
• The original content should appear.

Scenario 2 - Basic Menu Translate:

• A user on an English language device and app navigates to a French website.
• Navigate to the browser menu and select "Translate Page".
• A translations dialog will appear on the screen.
• Set "To" and "From" languages and press translate to begin translating.
• The page should begin to translate.

Scenario 3 - Translation Settings Changes:

• A user wishes to change their translation settings.
• Navigate to the browser menu and select "Translate Page".
• Navigate to the gear icon titled "Translation Options".
  • Toggle the different options.
• Go to "Translation settings" for more options as well.

Scenario 4 - Automatic Translations:

• A user sets the option to "Always translate French" to true on a French website as described in Scenario 3.
• A user on an English language device and app navigates to a French website.
• The page should automatically translate.

Scenario 5 - Low Data Flow

• Have the device set to "Data Saver Mode" in the OS settings. Turn WiFi off.
• Follow Scenario 1 or 2.
• A dialog should appear to warn a download will occur right after the translate button is pressed.

Note:
Any website page language may be used to test, so long is it is a supported language and different than the App (or OS) language.

When will this ship?

Considering an early or preview release in 126 with a limited population. We are releasing this feature via Nimbus, so we have a lot of control over feature shipping.

Tracking bug/issue:

All essentially the same, but different presentations of core bug lists:

• Bugzilla meta
• JIRA Parent
• Engineering Spreadsheet

Design documents (e.g. Product Requirements Document, UI spec):

• Figma

Engineering lead:

Olivia Hall

Product manager:

Marie-Lilas Onanga Ozavino

UI/UX contacts:

Dasha Andriyenko
Emily Wachowiak

The accessibility team has developed the Mozilla Accessibility Release Guidelines which outline what is needed to make user interfaces accessible:

https://wiki.mozilla.org/Accessibility/Guidelines
Please describe the accessibility guidelines you considered and what steps you've taken to address them:

• Designs included accessibility requirements and were reviewed by the a11y team
• Engineering team followed best practices for Android
• We are requesting implementation review to find additional bugs or issues

Describe any areas of concern to which you want the accessibility team to give special attention:

• Especially concerned with state management of this feature, such as translated v. untranslated state presentation and translation in progress.
• The feature has a lot of moving parts and would benefit from a general review.

The accessibility review is completed.

I'm marking the bug as Changes required since the bug 1884702 and bug 1884929 have higher affect on the a11y customers and are recommended to be resolved.

Changing the status to passed since both higher severity bugs have been resolved and closing the bug.